Which business objects for which jobs?

Cs* Objects for legacy tables

CS Business Objects (CsContact, CsActivity, …) are objects related to the areas of iMIS you are most familiar with. For example, CsContact is an object that combines data from the Name and Name_Fin tables into a single, simple-to-query object in a location that’s easy to find. Cs Business Objects are based on legacy iMIS tables.

Cs Business Objects are used in many instances. For example, if IQA is the only application running in your organization, you will use the CsObjects.

In addition, any tables built through the iMIS Customizer features will appear in the list of business objects as “CsName_” + TableName.

Commonly queried CsObjects include but are not limited to these:

When to use CsContact vs. NetContact

There are two versions of the Contact business object, one is called CsContact and the other is called NetContact.

■    Organizations that use Business Objects with IQA only can reliably use CsContact.

■    Organizations that are licensed for any component of the Marketing Suite or Process Manager should use NetContact. NetContact is a required object within those modules.

Objects for business rules

Many objects within the list of business objects control how different business rules, most importantly security rules, are managed within the database. These business objects are system objects and should not be modified.

These objects include but are not limited to these:

The Business Object Designer is your interface to managing the building of new business rule data such as object and property constraints. For example, a property constraint that manages the assignment of a task due date will write to the Access and Uniform objects and manage the rule from there.

Objects that support modules

In addition to the objects listed above, other objects (used specifically by Process Manager, Marketing Suite, or iMIS Web Components) are listed in the Business Object folder. These objects include but are not limited to:

■    Process Manager

□    OpportunityMember

□    OpportunitySales

□    OpportunityDonor

□    OppMemberContact

□    OppSalesContact

□    OppDonorContact

□    Opportunity

□    OpportunityHistory

□    OpportunityReport

□    OpportunityCompetitor

□    OpportunityType

□    ActionPlan

■    Campaign Management

□    Appeal

□    AppealParticipation

□    AppealProduct

□    Campaign

□    CampaignParticipation

□    CampaignTypeRef

□    Solicitation

□    SolicitationStatusRef

□    SourceCode

□    SourceCodeStatusRef

□    Package

□    PackageItem

□    PackageStatusRef

□    Supplement

■    Segmentation

□    SegmentationDef

□    SegmentationJob

□    SourceList

□    ListElement

■    RFM Analysis

□    RFM Analysis

■    Content Management

□    Document

□    DocumentStorage

□    Hierarchy (DocumentHierarchy, NavigationHierarchy, TagHierarchy)

□    Perspective

□    ContentChangeRequest

□    ContentWorkflow

□    NavigationPane

□    NavigationWorkflow

□    PublishMessageLog

□    PublishPriority

□    PublishRequest

□    PublishRequestDetail

□    PublishRequestStatus

□    PublishServer

□    TagRelationship

□    TagRelationshipType

□    UniformTag

□    URLMapping

□    UserDefinedField

□    WebPartGalleryEntry

Objects built from user-defined tables

When iMIS is first installed or upgraded, any user defined tables that are seen within the Customers area of iMIS are automatically built into business objects which can be queried.

As time goes by, it is often necessary to add new fields to Customers tabs and include those queries in IQA queries. This requires that a final step to complete the field addition after you have finished building the table and tab in Customers > System Set Up.